Use libunwind to find the boundary of sysimg functions on linux #14882
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
They don't appear in the symbol table and dladdr can't handle it.
|
lgtm |
|
There seems to be random test failures on AppVeyor even if this patch doesn't change any code on windows....... |
yuyichao
added a commit
that referenced
this pull request
Feb 1, 2016
Use libunwind to find the boundary of sysimg functions on linux
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They don't appear in the symbol table and
dladdrcan't handle it (on linux). This fixes the printing of function signatures for sysimg functions on linux.Using libunwind also means we'll have slightly better support for stripped debug info. We should add that support to
debuginfo.cpptoo but not this PR.